Hello,
According to your API docs (here: https://developer.pagerduty.com/api-reference/005299ed43553-get-an-incident), the get / create incident endpoints are supposed to return a conference_bridge object, but they are not. Is this a deliberate change? I recall this data being in the payload in the past but recently it hasn’t been.
Make sure you have include[]=conference_bridge in the request URL for the incident. I stumbled on this a few months back. While the conference_bridge is shown in the default return payload, it requires a query flag to be included.
Glancing back to the docs now, I don’t see it mentioned at all! 
Hi Matthew,
JC is correct! You can use the include[] parameter and enter a value of conference_bridge to return those details.
I wasn’t able to find any evidence of this being a recent change. So far I’ve been able to determine that this was the same behavior as far back as January 2020. I do see that it isn’t documented on our Get incidents endpoint, however it is documented on our List incidents endpoint. I’m happy to reach out to the team that manages this to see if the documentation can be made more consistent.
Let me know if you have any other questions!
Cassie Champagne
Technical Support Specialist
PagerDuty Support
Register now to join us for PagerDuty Summit 2022!
I just gave that a try and it unfortunately doesn’t work. I’m getting a 400 response when I send the request with include[]=conference_bridge. I also tried it as includes with and without the brackets, still getting a 400.
The conference_bridge should be a part of the default payload anyway, according to the docs. Please do reach out to the team about this since it seems like a mistake that conference_bridge is omitted.
Hi Matthew,
The URL for the request should look like the below for the Get incident endpoint:
https://api.pagerduty.com/incidents/:id?include[]=conference_bridge
And for the Create incident endpoint:
https://api.pagerduty.com/incidents?include[]=conference_bridge
If you’re still receiving a 400 error, I’d be happy to look into this further for you if you can reach out to us at support@pagerduty.com. Feel free to reference this post in your email.
Cassie Champagne
Technical Support Specialist
PagerDuty Support
Register now to join us for PagerDuty Summit 2022!